docs: credit contributors inline per change (GitHub renders the row from @mentions)#49
Conversation
Dependency Review✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.Scanned FilesNone |
github-actions
Bot
added
documentation
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
This pull request updates the release process documentation to address under-credited contributors, such as those from direct pushes or human co-authors of bot commits, by adding a helper git log command. The reviewer suggested improving this command by including email addresses and sorting the output to make mapping contributors to GitHub usernames easier.
Important
The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.
There was a problem hiding this comment.
Pull request overview
This PR updates the GitHub release skill’s release-process reference documentation to help detect under-credit in contributor harvesting—specifically for contributions that don’t show up as merged-PR authors (e.g., direct pushes and bot-authored commits with human co-authors/committers).
Changes:
- Adds guidance explaining two common under-credit scenarios (direct pushes; bot-authored commits with human committer/co-authors).
- Adds a suggested
git logcommand to identify the committer andCo-authored-bytrailer information for the relevant commit range.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
CybotTM
changed the title
CybotTM
changed the title
CybotTM
force-pushed
the
docs/harvest-under-credit-direct-push
branch
from
5ee2485 to
d49dbeb
Compare
…ributors row from @mentions The skill prescribed a hand-written `## Contributors` section built by harvest-contributors.sh. But GitHub already generates the Contributors avatar row from the `@mentions` in the body (mentions_count); a hand-written section duplicates that row and lumps everyone together, losing the per-change role. Policy now: `@mention` each contributor inline at the change they touched, by role (reporter / PR author / committer / co-author / reviewer / discussant); never hand-write a section. - SKILL.md step 9 and release-process.md Phase 5 + the crediting subsection rewritten to the inline policy. - harvest-contributors.sh repurposed from section generator to a who-contributed-to-what lookup (no `## Contributors` output). Pure helpers (extract_pr_numbers, is_bot) and the self-test are unchanged and still pass. - Kept the bidirectional harvest cross-check (over- and under-credit, incl. direct-push and bot-authored/human-co-authored commits). Signed-off-by: Sebastian Mendel <info@sebastianmendel.de>
CybotTM
force-pushed
the
docs/harvest-under-credit-direct-push
branch
from
d49dbeb to
1b9d5ff
Compare
|
The skill prescribed a hand-written
## Contributorssection (viaharvest-contributors.sh). But GitHub already builds the Contributors avatar row above Assets from the@mentionsin the release body (mentions_count) — a hand-written section duplicates it and lumps everyone together, losing who did what.New policy
@mentioneach contributor inline at the change they touched, by role — reporter, PR author, committer/co-author, reviewer, discussant. No hand-written section. Example:Changes
mentions_count) is now explicit.## Contributorsoutput). Pure helpers and the self-test are unchanged and pass.#Nfrom changelog excerpts /​) and under-credit (direct-push and bot-authored/human-co-authored commits, e.g.copilot-swe-agent[bot]where the human is the committer/co-author).